Re: [LANG] Next steps
2015-04-19 17:41 GMT+02:00 Benedikt Ritter brit...@apache.org: Hi, 3.4 has been released. GitHub badges have been activated. Now we can start the migration to git. Here is the Infra ticket [1] The git mirror has been created at https://git-wip-us.apache.org/repos/asf/commons-lang.git The SVN tree is now write only. Regards, Benedikt [1] https://issues.apache.org/jira/browse/INFRA-9478 2015-03-13 20:21 GMT+01:00 Gary Gregory garydgreg...@gmail.com: I like you'd plan! Gary :-) div Original message /divdivFrom: Benedikt Ritter brit...@apache.org /divdivDate:03/13/2015 11:17 (GMT-08:00) /divdivTo: Commons Developers List dev@commons.apache.org /divdivCc: /divdivSubject: [LANG] Next steps /divdiv /divHi all, I just want to give you an update on what I'm planning next for [lang]. - I'll review the pending patches and commit what is ready to be committed. - After that I'll cut 3.4 RC1 - After that I'll start the git migration (I hope that I have information about the github badges [1] until then, so that I can request INFRA to activate the corresponding services) Regards, Benedikt [1] http://markmail.org/message/umscsixafxy3rpnp -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
Re: [LANG] Next steps
Hi, 3.4 has been released. GitHub badges have been activated. Now we can start the migration to git. Here is the Infra ticket [1] Regards, Benedikt [1] https://issues.apache.org/jira/browse/INFRA-9478 2015-03-13 20:21 GMT+01:00 Gary Gregory garydgreg...@gmail.com: I like you'd plan! Gary :-) div Original message /divdivFrom: Benedikt Ritter brit...@apache.org /divdivDate:03/13/2015 11:17 (GMT-08:00) /divdivTo: Commons Developers List dev@commons.apache.org /divdivCc: /divdivSubject: [LANG] Next steps /divdiv /divHi all, I just want to give you an update on what I'm planning next for [lang]. - I'll review the pending patches and commit what is ready to be committed. - After that I'll cut 3.4 RC1 - After that I'll start the git migration (I hope that I have information about the github badges [1] until then, so that I can request INFRA to activate the corresponding services) Regards, Benedikt [1] http://markmail.org/message/umscsixafxy3rpnp -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
RE: [LANG] Next steps
I like you'd plan! Gary :-) div Original message /divdivFrom: Benedikt Ritter brit...@apache.org /divdivDate:03/13/2015 11:17 (GMT-08:00) /divdivTo: Commons Developers List dev@commons.apache.org /divdivCc: /divdivSubject: [LANG] Next steps /divdiv /divHi all, I just want to give you an update on what I'm planning next for [lang]. - I'll review the pending patches and commit what is ready to be committed. - After that I'll cut 3.4 RC1 - After that I'll start the git migration (I hope that I have information about the github badges [1] until then, so that I can request INFRA to activate the corresponding services) Regards, Benedikt [1] http://markmail.org/message/umscsixafxy3rpnp -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
[LANG] Next steps
Hi all, I just want to give you an update on what I'm planning next for [lang]. - I'll review the pending patches and commit what is ready to be committed. - After that I'll cut 3.4 RC1 - After that I'll start the git migration (I hope that I have information about the github badges [1] until then, so that I can request INFRA to activate the corresponding services) Regards, Benedikt [1] http://markmail.org/message/umscsixafxy3rpnp -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
Re: [LANG] Next steps
On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter brit...@apache.org wrote: Hello Hen 2014/1/3 Henri Yandell flame...@gmail.com Better move quick on 3.2.1. Only bit I don't like about that is that it implies we shouldn't be committing anything that would lead us to want to have a 3.3. I'm working on getting 3.2.1 RC1 out of the door this weekend. *cheer* :) I'm +1 for calendar defined minor releases btw. I think we should be releasing monthly, if anyone has the energy to deal with the RMing :) RMing is not such a big deal. I mean it's tedious, but it's okay, if you only have to to it once in a while. The problem is, that I don't see that much development activity. But let's see how the next weeks turn out. From my point of view, I tend to freeze up on activity when an RM is in the works. Sure we could develop in parallel etc, but it's mostly about the issue tracker and not developing lots of new features, so it's rare that something has a long active life on a separate branch. The last time I remember such was when I rewrote the text.translate stuff. So I'm holding off on doing too much while you're in RM mode. I think we'd benefit from a scheduled release cycle if you're up to handling it. An intent that we release at the end of every 1, 2, 3, something months. If we're releasing often, we shouldn't get sidetracked on the packaging as we'll know we can fix it soon and there will have been less time for any oddities to show up. Hen
Re: [LANG] Next steps
2014/1/4 Henri Yandell flame...@gmail.com On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter brit...@apache.org wrote: Hello Hen 2014/1/3 Henri Yandell flame...@gmail.com Better move quick on 3.2.1. Only bit I don't like about that is that it implies we shouldn't be committing anything that would lead us to want to have a 3.3. I'm working on getting 3.2.1 RC1 out of the door this weekend. *cheer* :) I'm +1 for calendar defined minor releases btw. I think we should be releasing monthly, if anyone has the energy to deal with the RMing :) RMing is not such a big deal. I mean it's tedious, but it's okay, if you only have to to it once in a while. The problem is, that I don't see that much development activity. But let's see how the next weeks turn out. From my point of view, I tend to freeze up on activity when an RM is in the works. What could be done is selecting issues we want to have in 3.3 and mark them as such in Jira. Sure we could develop in parallel etc, but it's mostly about the issue tracker and not developing lots of new features, so it's rare that something has a long active life on a separate branch. The last time I remember such was when I rewrote the text.translate stuff. Agreed, branching is a pain in svn but this my work out better after we switch to git. So I'm holding off on doing too much while you're in RM mode. I think we'd benefit from a scheduled release cycle if you're up to handling it. An intent that we release at the end of every 1, 2, 3, something months. If we're releasing often, we shouldn't get sidetracked on the packaging as we'll know we can fix it soon and there will have been less time for any oddities to show up. This sounds like you're not in the mood to RM yourself :-) I think I can manage to roll out a RC in the schedule you proposed. But it would be even better if we could rotate. Benedikt Hen -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
Re: [LANG] Next steps
On Sat, Jan 4, 2014 at 3:14 AM, Benedikt Ritter brit...@apache.org wrote: 2014/1/4 Henri Yandell flame...@gmail.com On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter brit...@apache.org wrote: Hello Hen 2014/1/3 Henri Yandell flame...@gmail.com I'm +1 for calendar defined minor releases btw. I think we should be releasing monthly, if anyone has the energy to deal with the RMing :) RMing is not such a big deal. I mean it's tedious, but it's okay, if you only have to to it once in a while. The problem is, that I don't see that much development activity. But let's see how the next weeks turn out. From my point of view, I tend to freeze up on activity when an RM is in the works. What could be done is selecting issues we want to have in 3.3 and mark them as such in Jira. I want anything whose patch gets reviewed :) Sure we could develop in parallel etc, but it's mostly about the issue tracker and not developing lots of new features, so it's rare that something has a long active life on a separate branch. The last time I remember such was when I rewrote the text.translate stuff. Agreed, branching is a pain in svn but this my work out better after we switch to git. Could be, though bear in mind I like merging in SVN so I'm saying the above from the project management side of lots of branches and doing clean up rather than the technicals of svn vs git. So I'm holding off on doing too much while you're in RM mode. I think we'd benefit from a scheduled release cycle if you're up to handling it. An intent that we release at the end of every 1, 2, 3, something months. If we're releasing often, we shouldn't get sidetracked on the packaging as we'll know we can fix it soon and there will have been less time for any oddities to show up. This sounds like you're not in the mood to RM yourself :-) I think I can manage to roll out a RC in the schedule you proposed. But it would be even better if we could rotate. Really not in the mood to RM :) My personal situation is such that I don't have large pieces of time to commit, instead it's 30min each night, and my experience in trying to RM has been that that isn't enough. Ideally it should be zero effort, it should be a case of: Every commit generates release artifacts needed for a vote. Automated alarm sends Should next Lang be released? to commons-dev. People focus on things being good for a week or so, then start to mark +1. Release done. Perhaps something to focus on at the next ApacheCon if there was interest. Hen
Re: [LANG] Next steps
On Sat, Jan 4, 2014 at 11:44 AM, Henri Yandell flame...@gmail.com wrote: On Sat, Jan 4, 2014 at 3:14 AM, Benedikt Ritter brit...@apache.orgwrote: 2014/1/4 Henri Yandell flame...@gmail.com On Fri, Jan 3, 2014 at 2:35 AM, Benedikt Ritter brit...@apache.org wrote: Hello Hen 2014/1/3 Henri Yandell flame...@gmail.com I'm +1 for calendar defined minor releases btw. I think we should be releasing monthly, if anyone has the energy to deal with the RMing :) RMing is not such a big deal. I mean it's tedious, but it's okay, if you only have to to it once in a while. The problem is, that I don't see that much development activity. But let's see how the next weeks turn out. From my point of view, I tend to freeze up on activity when an RM is in the works. What could be done is selecting issues we want to have in 3.3 and mark them as such in Jira. I want anything whose patch gets reviewed :) Sure we could develop in parallel etc, but it's mostly about the issue tracker and not developing lots of new features, so it's rare that something has a long active life on a separate branch. The last time I remember such was when I rewrote the text.translate stuff. Agreed, branching is a pain in svn but this my work out better after we switch to git. Could be, though bear in mind I like merging in SVN so I'm saying the above from the project management side of lots of branches and doing clean up rather than the technicals of svn vs git. So I'm holding off on doing too much while you're in RM mode. I think we'd benefit from a scheduled release cycle if you're up to handling it. An intent that we release at the end of every 1, 2, 3, something months. If we're releasing often, we shouldn't get sidetracked on the packaging as we'll know we can fix it soon and there will have been less time for any oddities to show up. This sounds like you're not in the mood to RM yourself :-) I think I can manage to roll out a RC in the schedule you proposed. But it would be even better if we could rotate. Really not in the mood to RM :) My personal situation is such that I don't have large pieces of time to commit, instead it's 30min each night, and my experience in trying to RM has been that that isn't enough. Ideally it should be zero effort, it should be a case of: Every commit generates release artifacts needed for a vote. Automated alarm sends Should next Lang be released? to commons-dev. People focus on things being good for a week or so, then start to mark +1. Release done. Perhaps something to focus on at the next ApacheCon if there was interest. Hen Crap. Just saw when ApacheCon is :( We'll be holding ApacheCon North America in Denver, Colorado, April 7-11, 2014. Stay tuned for more details and registration information. Managing to hit the only time on the calendar in 2014 that I'm committed to something and can't go travelling :( Hen
Re: [LANG] Next steps
Hello Hen 2014/1/3 Henri Yandell flame...@gmail.com Better move quick on 3.2.1. Only bit I don't like about that is that it implies we shouldn't be committing anything that would lead us to want to have a 3.3. I'm working on getting 3.2.1 RC1 out of the door this weekend. I'm +1 for calendar defined minor releases btw. I think we should be releasing monthly, if anyone has the energy to deal with the RMing :) RMing is not such a big deal. I mean it's tedious, but it's okay, if you only have to to it once in a while. The problem is, that I don't see that much development activity. But let's see how the next weeks turn out. Benedikt Hen On Thu, Jan 2, 2014 at 8:56 PM, Henri Yandell flame...@gmail.com wrote: Also +1 to all. On Thu, Jan 2, 2014 at 6:40 AM, Gary Gregory garydgreg...@gmail.com wrote: +1 to it all. Gary Original message From: Benedikt Ritter brit...@apache.org Date:01/02/2014 05:29 (GMT-05:00) To: Commons Developers List dev@commons.apache.org Subject: [LANG] Next steps Hi all, I've successfully gone through my first release (wasn't as bad as I had expected it to be). I still have to do the Jira stuff, will do that tonight probably. So, here is what I have in mind for lang as next steps. Move User Guide from Website to package-info.java: The user guide is structured in terms of packages in lang. It looks like the package-info.java files are better suited for this kind of information. Since Lang isn't a framework where multiple parts play together, I don't see the need for a real user guide. Push out 3.2.1: Although the two issues identified by Oliver and Jörg didn't block release 3.2, I'd like to push out a bugfix (probably containing the above changes) Move to git: We have talked about this a lot, and I had the feeling, that the people working on [lang] are fine with moving to git. I'm planning to work out a little guide on how to work on issues, create branches, create releases using git. But this will probably take a while. Thoughts? Benedikt -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
[LANG] Next steps
Hi all, I've successfully gone through my first release (wasn't as bad as I had expected it to be). I still have to do the Jira stuff, will do that tonight probably. So, here is what I have in mind for lang as next steps. Move User Guide from Website to package-info.java: The user guide is structured in terms of packages in lang. It looks like the package-info.java files are better suited for this kind of information. Since Lang isn't a framework where multiple parts play together, I don't see the need for a real user guide. Push out 3.2.1: Although the two issues identified by Oliver and Jörg didn't block release 3.2, I'd like to push out a bugfix (probably containing the above changes) Move to git: We have talked about this a lot, and I had the feeling, that the people working on [lang] are fine with moving to git. I'm planning to work out a little guide on how to work on issues, create branches, create releases using git. But this will probably take a while. Thoughts? Benedikt -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
RE: [LANG] Next steps
+1 to it all. Gary Original message From: Benedikt Ritter brit...@apache.org Date:01/02/2014 05:29 (GMT-05:00) To: Commons Developers List dev@commons.apache.org Subject: [LANG] Next steps Hi all, I've successfully gone through my first release (wasn't as bad as I had expected it to be). I still have to do the Jira stuff, will do that tonight probably. So, here is what I have in mind for lang as next steps. Move User Guide from Website to package-info.java: The user guide is structured in terms of packages in lang. It looks like the package-info.java files are better suited for this kind of information. Since Lang isn't a framework where multiple parts play together, I don't see the need for a real user guide. Push out 3.2.1: Although the two issues identified by Oliver and Jörg didn't block release 3.2, I'd like to push out a bugfix (probably containing the above changes) Move to git: We have talked about this a lot, and I had the feeling, that the people working on [lang] are fine with moving to git. I'm planning to work out a little guide on how to work on issues, create branches, create releases using git. But this will probably take a while. Thoughts? Benedikt -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
Re: [LANG] Next steps
On 2 January 2014 14:40, Gary Gregory garydgreg...@gmail.com wrote: +1 to it all. Gary Original message From: Benedikt Ritter brit...@apache.org Date:01/02/2014 05:29 (GMT-05:00) To: Commons Developers List dev@commons.apache.org Subject: [LANG] Next steps Hi all, I've successfully gone through my first release (wasn't as bad as I had expected it to be). I still have to do the Jira stuff, will do that tonight probably. So, here is what I have in mind for lang as next steps. Move User Guide from Website to package-info.java: The user guide is structured in terms of packages in lang. It looks like the package-info.java files are better suited for this kind of information. Since Lang isn't a framework where multiple parts play together, I don't see the need for a real user guide. Push out 3.2.1: Although the two issues identified by Oliver and Jörg didn't block release 3.2, I'd like to push out a bugfix (probably containing the above changes) Move to git: We have talked about this a lot, and I had the feeling, that the people working on [lang] are fine with moving to git. I'm planning to work out a little guide on how to work on issues, create branches, create releases using git. But this will probably take a while. Thoughts? Benedikt -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter Sounds great to me. I think we also need to focus on a faster release cycle. The idea of release early, release often is regularly quoted by people on the ML, yet it took us over two years to move from 3.1 to 3.2. It would be nice to see a smaller feature set in each release, thus allowing for more regular releases. Thanks for getting 3.2 out the door! Duncan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [LANG] Next steps
2014/1/2 Duncan Jones djo...@cantab.net On 2 January 2014 14:40, Gary Gregory garydgreg...@gmail.com wrote: +1 to it all. Gary Original message From: Benedikt Ritter brit...@apache.org Date:01/02/2014 05:29 (GMT-05:00) To: Commons Developers List dev@commons.apache.org Subject: [LANG] Next steps Hi all, I've successfully gone through my first release (wasn't as bad as I had expected it to be). I still have to do the Jira stuff, will do that tonight probably. So, here is what I have in mind for lang as next steps. Move User Guide from Website to package-info.java: The user guide is structured in terms of packages in lang. It looks like the package-info.java files are better suited for this kind of information. Since Lang isn't a framework where multiple parts play together, I don't see the need for a real user guide. Push out 3.2.1: Although the two issues identified by Oliver and Jörg didn't block release 3.2, I'd like to push out a bugfix (probably containing the above changes) Move to git: We have talked about this a lot, and I had the feeling, that the people working on [lang] are fine with moving to git. I'm planning to work out a little guide on how to work on issues, create branches, create releases using git. But this will probably take a while. Thoughts? Benedikt -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter Sounds great to me. I think we also need to focus on a faster release cycle. The idea of release early, release often is regularly quoted by people on the ML, yet it took us over two years to move from 3.1 to 3.2. It would be nice to see a smaller feature set in each release, thus allowing for more regular releases. It always depends on peoples interests and their spare time. But yes, it took way to long for 3.2 to be released. Thanks for getting 3.2 out the door! Duncan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
Re: [LANG] Next steps
Also +1 to all. On Thu, Jan 2, 2014 at 6:40 AM, Gary Gregory garydgreg...@gmail.com wrote: +1 to it all. Gary Original message From: Benedikt Ritter brit...@apache.org Date:01/02/2014 05:29 (GMT-05:00) To: Commons Developers List dev@commons.apache.org Subject: [LANG] Next steps Hi all, I've successfully gone through my first release (wasn't as bad as I had expected it to be). I still have to do the Jira stuff, will do that tonight probably. So, here is what I have in mind for lang as next steps. Move User Guide from Website to package-info.java: The user guide is structured in terms of packages in lang. It looks like the package-info.java files are better suited for this kind of information. Since Lang isn't a framework where multiple parts play together, I don't see the need for a real user guide. Push out 3.2.1: Although the two issues identified by Oliver and Jörg didn't block release 3.2, I'd like to push out a bugfix (probably containing the above changes) Move to git: We have talked about this a lot, and I had the feeling, that the people working on [lang] are fine with moving to git. I'm planning to work out a little guide on how to work on issues, create branches, create releases using git. But this will probably take a while. Thoughts? Benedikt -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
Re: [LANG] Next steps
Better move quick on 3.2.1. Only bit I don't like about that is that it implies we shouldn't be committing anything that would lead us to want to have a 3.3. I'm +1 for calendar defined minor releases btw. I think we should be releasing monthly, if anyone has the energy to deal with the RMing :) Hen On Thu, Jan 2, 2014 at 8:56 PM, Henri Yandell flame...@gmail.com wrote: Also +1 to all. On Thu, Jan 2, 2014 at 6:40 AM, Gary Gregory garydgreg...@gmail.comwrote: +1 to it all. Gary Original message From: Benedikt Ritter brit...@apache.org Date:01/02/2014 05:29 (GMT-05:00) To: Commons Developers List dev@commons.apache.org Subject: [LANG] Next steps Hi all, I've successfully gone through my first release (wasn't as bad as I had expected it to be). I still have to do the Jira stuff, will do that tonight probably. So, here is what I have in mind for lang as next steps. Move User Guide from Website to package-info.java: The user guide is structured in terms of packages in lang. It looks like the package-info.java files are better suited for this kind of information. Since Lang isn't a framework where multiple parts play together, I don't see the need for a real user guide. Push out 3.2.1: Although the two issues identified by Oliver and Jörg didn't block release 3.2, I'd like to push out a bugfix (probably containing the above changes) Move to git: We have talked about this a lot, and I had the feeling, that the people working on [lang] are fine with moving to git. I'm planning to work out a little guide on how to work on issues, create branches, create releases using git. But this will probably take a while. Thoughts? Benedikt -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
