Hey All,
The following is based on previous release plans. Let me know if there's anything missing. One thing I want to do differently is the bug hunt. No score for this release, only going for bugs milestoned for 0.49 instead. This also means we need to hit the tracker to ensure the milestoned ones are correct and to milestone and must fixes. The number of bugs already fixed in trunk is huge, so getting the work out for further testing "soon" is better. Dates are subject to change as always, hopefully they could be moved up (with the exception of the the time between Feature Freeze and Hard Freeze, for the sake of the translators). Translators, I would recommend getting started sooner rather than later.
1. Open development. (In Progress)
2. Chill. (September 21, 2012) Development focuses on wrapping up. No further refactoring. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes. Update tutorials and other docs
3. Frost. (October 5, 2012) Most development complete. Release Notes should be >90% filled in. Bug Hunt: Target those milestoned for 0.49. Post alpha quality tarball.
4. Feature Freeze. (October 26, 2012) No further development work. Disable features that can't be finished in time. Focus on critical bug fixing. Finalize all tutorials, docs, etc. Finalize all extensions. Translators create/update translations. Inkscape must pass 'make distcheck' Post beta quality tarball.
5. Hard freeze. (November 23, 2012) Only release wardens can commit to mainline. No further string changes. Focus on release-critical bug fixing. Finalize translations, release notes, etc. Post Release Candidate tarball. Packagers test creating pkgs.
6. Branch. (December 7, 2012) Establish the Stable Branch for release Complete any late-late-late work. Final verification of packaging, release notes, docs, etc. Publish more release candidates until ready for release. Plan 0.49.1+ release(s), as needed
7. Release. (December 21, 2012) Post inkscape-0.49.tar.gz Post packages Post official announcements
8. Open development.
Yes, it seems like a ridiculously short timeframe given our history of making releases happen and how much we've strayed in the past. I do however feel it is doable given the change in the bug hunt requirement for this cycle. That usually holds us up. Also, no platform specific bugs will hold up this release. We will release for specific platforms as issues are taken care of.
If anyone has objections or concerns, please speak up. As stated in the past... this is doable. We're good, we're smart, we're competent, and we have the resources... we just need to be focused to make this happen. Let's do this!
Cheers, Josh
On Tue, Aug 28, 2012 at 11:03 PM, Josh Andler wrote:
- Release. (December 21, 2012) Post inkscape-0.49.tar.gz Post packages Post official announcements
No comments from me other than it's dangerously close to Xmas and a variety of other religious holidays. Sounds like a call for failure to me.
Alexandre Prokoudine http://libregraphicsworld.org
On Tue, Aug 28, 2012 at 12:10 PM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
No comments from me other than it's dangerously close to Xmas and a variety of other religious holidays. Sounds like a call for failure to me.
I agree that it's dangerously close... but the only place I could trim time would be the timeframe we allot mainly for translations. It seems greatly unfair to do so given the number of string changes we've had. However, if I can convince them to get started at Feature Freeze time, perhaps we could agree to reducing it by 1 week.
Again, we may be able to luck out and be able to trim other times more if our devs really hammer the bug fixing. Provided he's not too busy, I think the way John Smith has been hammering bugs, this could be a reality.
Cheers, Josh
On 28 August 2012 20:23, Josh Andler <scislac@...400...> wrote:
On Tue, Aug 28, 2012 at 12:10 PM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
No comments from me other than it's dangerously close to Xmas and a variety of other religious holidays. Sounds like a call for failure to me.
I agree that it's dangerously close... but the only place I could trim time would be the timeframe we allot mainly for translations.
So, how about extending it instead to hit just after the New Year? It seems to me that many contributors might be able to commit more time over the festive period?
M.
On Tue, Aug 28, 2012 at 12:57 PM, Marcin Floryan <mfloryan@...1877...> wrote:
So, how about extending it instead to hit just after the New Year? It seems to me that many contributors might be able to commit more time over the festive period?
If I'm remembering correctly, things typically get slow for a few days around Xmas in particular. We could always shoot for the 30th instead... but feels a little odd since it's between holidays. Either way, I want to see it released before the end of the year. By the end of 2012 has been the official response when people have been asking when it will be out.
Cheers, Josh
Didnt we aim for around new year with one before, and the 'people will have time over the holidays' theory proved to be wrong? (or rather people did have time, they just wanted to spend it with family, quite rightly!) I'd much prefer to be getting it out before the holidays than in them. Is there a reason to wait till late sept to launch an about screen contest? cant we kick that off in the next couple of weeks? I'd rather give people a decent timescale and not be rushing it. Cant we do a string chill a lot sooner too, if new features arent in there by the end of sept then they should be waiting till next release?
just some thoughts
Cheers
John
On Tue, Aug 28, 2012 at 11:40 PM, Josh Andler <scislac@...400...> wrote:
On Tue, Aug 28, 2012 at 12:57 PM, Marcin Floryan <mfloryan@...1877...> wrote:
So, how about extending it instead to hit just after the New Year? It seems to me that many contributors might be able to commit more time over the festive period?
If I'm remembering correctly, things typically get slow for a few days around Xmas in particular. We could always shoot for the 30th instead... but feels a little odd since it's between holidays. Either way, I want to see it released before the end of the year. By the end of 2012 has been the official response when people have been asking when it will be out.
Cheers, Josh
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Tue, Aug 28, 2012 at 3:54 PM, John Cliff <john.cliff@...400...> wrote:
Didnt we aim for around new year with one before, and the 'people will have time over the holidays' theory proved to be wrong? (or rather people did have time, they just wanted to spend it with family, quite rightly!)
I thought that was the case.
I'd much prefer to be getting it out before the holidays than in them. Is there a reason to wait till late sept to launch an about screen contest? cant we kick that off in the next couple of weeks?
A) We don't have a theme yet. B) Unless someone gets right on the "blocker" bugs, I'd rather expose users to them less.
We certainly can bump it up though if that's what more people are interested in.
I'd rather give people a decent timescale and not be rushing it. Cant we do a string chill a lot sooner too, if new features arent in there by the end of sept then they should be waiting till next release?
So, combine chill, frost, & feature freeze for roughly a month out? I know that Johan is on a short vacation and probably won't be able to chime in very soon. I'd like to have his thoughts.
Cheers, Josh
On Wed, Aug 29, 2012 at 2:54 AM, John Cliff wrote:
Cant we do a string chill a lot sooner too, if new features arent in there by the end of sept then they should be waiting till next release?
I suggest:
1. We do the frigging list of new features still to be added. 2. Figure out if any new messages could come rushing in. 3. Check all the new and old dialogs for possible fixes.
Then we shall know if we can do strings chill earlier.
Step 3 is optional, but we've changed so much in this development cycle that I'll be damned if we don't need to adjust this or that.
Alexandre Prokoudine http://libregraphicsworld.org
On Tue, Aug 28, 2012 at 11:01 PM, Alexandre Prokoudine <alexandre.prokoudine@...400...> wrote:
On Wed, Aug 29, 2012 at 2:54 AM, John Cliff wrote:
Cant we do a string chill a lot sooner too, if new features arent in there by the end of sept then they should be waiting till next release?
I suggest:
- We do the frigging list of new features still to be added.
John Smith is rapidly adding new features that are pretty complete on a very quick basis, that makes this less feasible unless we allow his work on those items to be accepted until X date. There's a good chance the GSoC projects will just be skipped for this cycle as they're not ready nor necessary and if we move to a more rapid cycle moving forward, it won't be long until they're included.
- Figure out if any new messages could come rushing in.
A lot of John's work involves preferences and string changes. John is a hero for the project, he's tackling a ton of our oldest reports. The more of those closed for 0.49, the more a majority of our users will feel it was worth the wait.
- Check all the new and old dialogs for possible fixes.
Do you mean in terms of what we are looking to modify prior to release?
Cheers, Josh
Just following up...
Is everyone still okay with us hitting Chill on Friday? Any objections?
As a reminder:
2. Chill. (September 21, 2012) Development focuses on wrapping up. No further refactoring. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes Update tutorials and other docs
Note: We have a known security issue that is in a bug report. If anyone would seriously be interested in fixing it, I can give you access to it. This bug report would also be the only real issue left for 0.48.4 as well.
As for the About Screen contest... what about a theme of "re-birth" or awakening from hibernation, or something along those lines of "we've been quiet, but we're back and more awesome".
Cheers, Josh
On 18-9-2012 21:11, Josh Andler wrote:
Just following up...
Is everyone still okay with us hitting Chill on Friday? Any objections?
As a reminder:
- Chill. (September 21, 2012) Development focuses on wrapping up. No further refactoring. Identify 'make distcheck' issues Triage bug reports Run an About Screen contest First draft of Release Notes Update tutorials and other docs
The guides project is not yet ready to be merged, but regarding the new-style-rework only the backwards compatibility issue is left which can be done quickly (I can take over if needs be). But I think it is OK if we hold off with this forward compatibility breaking change. There is no need for it at the moment. Grids will also need a forward compatibility breaking change, so we can synchronize it with guides if we postpone new-style guides to 0.50. And then rotatable desktop in 0.50? ;-)
For me this means I can (and should) focus on polishing PowerStroke as much as I can. (is it already clear if it will be in 0.49?)
Note: We have a known security issue that is in a bug report. If anyone would seriously be interested in fixing it, I can give you access to it. This bug report would also be the only real issue left for 0.48.4 as well.
Have a look at my comments for the bug. The proposed fix is very easy and can even be made optional if someone really wants that functionality.
As for the About Screen contest... what about a theme of "re-birth" or awakening from hibernation, or something along those lines of "we've been quiet, but we're back and more awesome".
:-)
ciao, Johan
On Wed, Sep 19, 2012 at 2:20 PM, Johan Engelen <jbc.engelen@...2592...> wrote:
The guides project is not yet ready to be merged, but regarding the new-style-rework only the backwards compatibility issue is left which can be done quickly (I can take over if needs be). But I think it is OK if we hold off with this forward compatibility breaking change. There is no need for it at the moment. Grids will also need a forward compatibility breaking change, so we can synchronize it with guides if we postpone new-style guides to 0.50. And then rotatable desktop in 0.50? ;-)
I think that if we are going to break compatibility, we go for one release to do it. Basically, all of the new-style stuff including custom doc coords would be a huge win to introduce all at once. I would love to see a rotatable canvas in Inkscape, but I have no idea how feasible it is with the current rendering/viewport stuff we have in place.
For me this means I can (and should) focus on polishing PowerStroke as much as I can. (is it already clear if it will be in 0.49?)
It's in the release notes, so I hope so. :) I would say yes, focusing on polishing this is definitely the best use of your time imho. Likewise, if you feel there are other experimental LPEs which we can bump to stable, why not shoot for that as well? Note: I have no idea which are which as my builds always include the experimental ones.
Have a look at my comments for the bug. The proposed fix is very easy and can even be made optional if someone really wants that functionality.
I'm primarily concerned about if we accidentally break something. I will try to see if I can catch JonCruz to get his input.
Cheers, Josh
2012/9/19 Josh Andler <scislac@...400...>:
I think that if we are going to break compatibility, we go for one release to do it. Basically, all of the new-style stuff including custom doc coords would be a huge win to introduce all at once. I would love to see a rotatable canvas in Inkscape, but I have no idea how feasible it is with the current rendering/viewport stuff we have in place.
In principle it should be possible to change doc2dt and dt2doc matrices to any transform without any modifications to the display subsystem, but it might expose bugs - mainly hidden assumptions that doc2dt is always an Y flip + translation.
The code drawing the page background will need to be rewritten, as it now assumes that the page is a rectangle with sides parallel to desktop coordinate system axes.
Regards, Krzysztof
On Tue, 2012-08-28 at 23:19 -0700, Josh Andler wrote:
John Smith is rapidly adding new features that are pretty complete on a very quick basis
He's never posted to the list AFAICS and it's a really hard name to search for. who is John Smith the Inkbug slayer?
Martin,
On Wed, Aug 29, 2012 at 8:15 PM, Martin Owens <doctormo@...400...> wrote:
He's never posted to the list AFAICS and it's a really hard name to search for. who is John Smith the Inkbug slayer?
https://launchpad.net/~john-smithi
Take a look at the Wishlist section and also take a look at the number of low number (old) reports he's been closing.
https://bugs.launchpad.net/inkscape/+bugs?field.searchtext=&orderby=-imp...
Cheers, Josh
On 08/30/2012 06:15 AM, Josh Andler wrote:
On Wed, Aug 29, 2012 at 8:15 PM, Martin Owens <doctormo@...400...> wrote:
He's never posted to the list AFAICS and it's a really hard name to search for. who is John Smith the Inkbug slayer?
https://launchpad.net/~john-smithi
Take a look at the Wishlist section and also take a look at the number of low number (old) reports he's been closing.
https://bugs.launchpad.net/inkscape/+bugs?field.searchtext=&orderby=-imp...
Yes, we know what he did (which is amazing!), but we still don't know who he is!
Martin, I've been wondering the exact same thing. LinkedIn hasn' t been very helpful. Where do we send the flowers to?
Regards,
Diederik
A number of people choose not to share this information. Tavmjong Bah, bulia byak, MenTaLguY, ~suv, and others choose to not be openly public about who they are in real life.
I ask that people remain respectful about contributors'/anyone's wishes for privacy.
I'm not saying John is asking for privacy, I don't know how he feels honestly. I'm just saying we need to be respectful of the wishes of others (in some cases, even asking them is crossing a line). John Smith could just be a pseudonym to make him or her harder to identify. (Note: I have no leanings or opinions about John's identity)
Cheers, Josh On Aug 29, 2012 11:16 PM, "Diederik van Lierop" <mail@...1689...> wrote:
On 08/30/2012 06:15 AM, Josh Andler wrote:
On Wed, Aug 29, 2012 at 8:15 PM, Martin Owens <doctormo@...400...>
wrote:
He's never posted to the list AFAICS and it's a really hard name to search for. who is John Smith the Inkbug slayer?
https://launchpad.net/~john-smithi
Take a look at the Wishlist section and also take a look at the number of low number (old) reports he's been closing.
https://bugs.launchpad.net/inkscape/+bugs?field.searchtext=&orderby=-imp...
Yes, we know what he did (which is amazing!), but we still don't know who he is!
Martin, I've been wondering the exact same thing. LinkedIn hasn' t been very helpful. Where do we send the flowers to?
Regards,
Diederik
Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 2012-08-30 09:22, Josh Andler wrote:
A number of people choose not to share this information. Tavmjong Bah, bulia byak, MenTaLguY, ~suv, and others choose to not be openly public about who they are in real life.
Yes, I can see why some would prefer that. But at least three of the names you mentioned are googleable ;-)
I ask that people remain respectful about contributors'/anyone's wishes for privacy.
Of course, that goes without saying! It's only natural though for people to become curious when they spot a mystery I guess.
Regards,
Diederik
On Thu, Aug 30, 2012 at 12:37 AM, Diederik van Lierop <mail@...1689...> wrote:
Yes, I can see why some would prefer that. But at least three of the names you mentioned are googleable ;-)
Even though you mean no harm, this was an inappropriate thing to share. Chances are someone else shared the info and not themselves (which doubles down on how inappropriate their actions were).
Of course, that goes without saying! It's only natural though for people to become curious when they spot a mystery I guess.
I don't disagree... but we also need to not let our nature dictate our actions. Especially to openly discuss such things in a public forum such as a mailing list. As an American, this is a particularly sensitive subject to me (the spying done by our telecoms and government). Curiosity (or in our case unmerited suspicion) does not grant open license to really look into.
Cheers, Josh
On 08/30/2012 10:08 AM, Josh Andler wrote:
On Thu, Aug 30, 2012 at 12:37 AM, Diederik van Lierop <mail@...1689...> wrote:
Yes, I can see why some would prefer that. But at least three of the names you mentioned are googleable ;-)
Even though you mean no harm, this was an inappropriate thing to share.
The only thing I tried to point out is that a unique name helps searching for them, which I tend to do because I like to read my co-developper's blogs, forum-posts, books, and even interviews. i guess that this makes me feel more connected to this community, as I get to know people better. I like to know what people do for a living, where they studied, and what makes them tick.
I didn't have the intention to share anything inappropriate, and I am sorry if I did.
Kind regards,
Diederik
Hi all
Can we close this conversation? It is not only filling mail boxes but is also quickly going off-topic and, in addition, is not so relevant for the project. ;-) Let's thank JS for all the things he's doing ...
Kind regards K
Sorry list about the OT
On Thu, 2012-08-30 at 00:22 -0700, Josh Andler wrote:
choose to not be openly public about who they are in real life.
Of course, all the people you sight have created a recognizable pseudo brand :-D they're reputation is assured. Zuro and Superman can be thanked, John Smith is that damn everyman hero instead.
in some cases, even asking them is crossing a line
Asking questions should never cross a line. The presumption in the UCoC is that people mean what they say and are not coloring in between the lines. Treat people with the respect and assume good faith, including questions which I think should be assumed to be honestly asked.
We don't have to press for an answer though. I'm happy.
Martin,
On Thu, Aug 30, 2012 at 7:56 PM, Martin Owens wrote:
Asking questions should never cross a line. The presumption in the UCoC
University church of Christ? University Committee on Committees? UConn Outing Club?
Alexandre Prokoudine http://libregraphicsworld.org
On Thu, 2012-08-30 at 20:01 +0400, Alexandre Prokoudine wrote:
University church of Christ? University Committee on Committees? UConn Outing Club?
Either Ubuntu's Code of Conduct or the Universal Church of Cthulhu. They're both pretty big on tolerance and awaking elder gods.
Martin,
On Wed, Aug 29, 2012 at 8:15 PM, Martin Owens <doctormo@...400...> wrote:
He's never posted to the list AFAICS and it's a really hard name to search for. who is John Smith the Inkbug slayer?
As a quick note, he has indeed posted to the list a handful of times... I used basic Google/Gmail-fu and found the posts in one search.
Cheers, Josh
On Thu, Aug 30, 2012 at 7:15 AM, Martin Owens wrote:
He's never posted to the list AFAICS and it's a really hard name to search for. who is John Smith the Inkbug slayer?
Oh, who is John Galt? :)
Alexandre Prokoudine http://libregraphicsworld.org
On Tue, 2012-08-28 at 12:23 -0700, Josh Andler wrote:
be the timeframe we allot mainly for translations
I thought the idea behind tracks in launchpad translations was so we could release translation updates for a specific release after the main functional release.
It would certainly encourage translators to get strings in on time for the release if all we could promise after that was an update to fix the strings.
Martin,
participants (9)
-
Alexandre Prokoudine -
Diederik van Lierop -
Johan Engelen -
John Cliff -
Josh Andler -
Kris De Gussem -
Krzysztof Kosiński -
Marcin Floryan -
Martin Owens